Skip to content

[Motions 2025 06 lwg 1] P3742R0 C++ Standard Library Issues #8014

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 24 commits into
base: main
Choose a base branch
from

Conversation

burblebee
Copy link
Contributor

@burblebee burblebee commented Jun 25, 2025

Fixes #7938

burblebee added 24 commits June 24, 2025 22:49
…er itself instead of its child

[exec.let] Added : before codeblock for consistency.
[expected.object.cons]p23.2 Fly-by fix expression (">" in wrong place).
@burblebee burblebee marked this pull request as ready for review June 25, 2025 21:59
Copy link
Member

@Eisenwave Eisenwave left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

There are some \linebreaks introduced which should be \brk{}; otherwise I couldn't find anything wrong.

There are also some index entries added for exposition-only stuff, and I'm not sure if that's usually done.

@burblebee
Copy link
Contributor Author

burblebee commented Jul 12, 2025

There are some \linebreaks introduced which should be \brk{}; otherwise I couldn't find anything wrong.

As I understand it, \brk (aka \discretionary) is basically \-, and I use \- where ever possible. So the fact that I resorted to \linebreak most likely meant that \brk wouldn't work in those cases. Do you know of any cases where using \brk would have made a difference?

@burblebee burblebee requested a review from Eisenwave July 12, 2025 09:16
@Eisenwave
Copy link
Member

Eisenwave commented Jul 12, 2025

As I understand it, \brk (aka \discretionary) is basically \-, and I use \- where ever possible.

Yeah, with the exception that it won't leave a hyphen at line wraps (unless \discretionary is configured to do so, which it isn't for \brk).

So the fact that I resorted to \linebreak most likely meant that \brk wouldn't work in those cases. Do you know of any cases where using \brk would have made a difference?

Can you just replace any use of \linebreak with \brk{} and see if that fixes it? I have drafted up many thousands of TeX LOCs for these motions, and I yet have to encounter a case where \linebreak works but \brk doesn't.

\- sometimes doesn't work because it's not in the right spot for paragraph justification to feel incentivized enough to break the line there, but if you throw in enough \-s in the midlde of words and \brk{} after punctuation etc., then it always seems to work. It's just a matter of drowning the \tcodes in enough line break opportunities until it works.

Jens also replaced a bunch of \linebreaks with \brks and that worked just fine in any of his PRs.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

[2025-06 LWG Motion 1] P3742R0 C++ Standard Library Issues to be moved in Sofia, Jun. 2025
2 participants